What I did

• add where condition to findMany method
  • Infer column type InferColumnsType to know the database type of columns being filtered
  • Formulate permissible operations for each field, using ColumnExpression.
  • Support nested queries, such as AndExpression, OrExpression, and NotExpression.
    See filter.spec.ts for usage.
  • Transform query object to drizzle's SQL condition with transformQueryObjectToSQL
    See the transformQueryObjectToSQL test for reference.
• Add a /admin/collections/custom-food-page page to demonstrate how to use the where condition.
  • Using a form consists of name, isCooked, and cookingType fields that will change the page's query once submitted to filter out data. See Display component for reference.
  • The filter logic is placed at server-component page.tsx

And why I did it

Why not?

Just kidding;

Because currently the server doesn't have filter functionality. The only way to do this is via client-side, which will be sophisticated and troublesome; i.e., filtering data that are limited to the first n records would give the user an incomplete result.

Nevertheless, providing a trivial filter, such as like would not be sufficient for real-world use cases. So it's better to give them all operators that drizzle provided. Along with type-safety capability, that would help developers from foot-gunning themselves by mistyping or unknowingly using the where filter in a misconceived way.

And I believe that supporting nested query, i.e.,

{
  "$or": [
    {
      "$and": [
        { "text": { "$like": "%A%" } },
        {
          "$or": [
            { "smallint": { "$inArray": [4, 3, 2, 1] } },
            { "real": { "$gte": 30 } }
          ]
        }
      ]
    }
  ],
  "boolean": { "$eq": true }
}

is necessary for, possibly, complex filtering use cases.

The added /admin/collections/custom-food-page is intended to demonstrate how to use a filter in source code.